-
Notifications
You must be signed in to change notification settings - Fork 460
fix RBAC upgrade #4956
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix RBAC upgrade #4956
Conversation
|
/test pull-cluster-api-provider-azure-apiversion-upgrade |
|
good catch! /lgtm |
|
LGTM label has been added. Git tree hash: f7c70a68ddc1c4c95770806011901a1a4bb022b1
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jackfrancis The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold for upgrade test |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4956 +/- ##
=======================================
Coverage 62.22% 62.22%
=======================================
Files 201 201
Lines 16886 16886
=======================================
Hits 10508 10508
Misses 5585 5585
Partials 793 793 ☔ View full report in Codecov by Sentry. |
|
/test pull-cluster-api-provider-azure-e2e-aks FYI @jackfrancis I'm not sure I've seen this kind of error before in the workload ID setup stuff: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-azure/4956/pull-cluster-api-provider-azure-e2e-aks/1807834346007040000 |
My best guess would be a flake in the |
|
#4264 |
|
Upgrade test is green, others look like flakes. |
|
/test pull-cluster-api-provider-azure-e2e |
1 similar comment
|
/test pull-cluster-api-provider-azure-e2e |
|
@nojnhuh: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This message doesn't make sense given canadacentral currently has 5 IPs allocated and southcentralus currently has 35. I'll try one more time to see if I get lucky and look into this more tomorrow. /test pull-cluster-api-provider-azure-e2e |
What type of PR is this?
/kind failing-test
What this PR does / why we need it: The tests that upgrade CAPZ don't agree with #4933 because it changed the ClusterRole referred to by the ClusterRoleBinding for the CAPZ controller manager which Kubernetes doesn't allow. This change does some light name swizzling to keep the names the same from previous releases while keeping the new aggregated role functionality.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
TODOs:
Release note: